Device including image with multiple layers

ABSTRACT

A mobile device is disclosed. The method device includes an image including a transactional image layer and a master image layer. The mobile device can be used to conduct transactions.

CROSS-REFERENCE TO RELATED PATENTS

The present U.S. Utility Patent Application claims priority pursuant to 35 U.S.C. § 119(e) to U.S. Provisional Application Ser. No. 61/091,343, entitled “Credit Card Imaging for Mobile Payment and Other Applications,” (Attorney Docket No. P-14202US), filed Aug. 23, 2008, pending, which is hereby incorporated herein by reference in its entirety and made part of the present U.S. Utility Patent Application for all purposes.

STATEMENT REGARDING FEDERALLY SPONSORED RESEARCH OR DEVELOPMENT

Not applicable.

INCORPORATION-BY-REFERENCE OF MATERIAL SUBMITTED ON A COMPACT DISC

Not applicable.

BACKGROUND OF THE INVENTION Technical field of the invention

This invention relates generally to financial transactions and more particularly to credit card imaging.

Description of related art

Millions of credit card transactions are accurately processed every day regardless of whether the purchaser is making a purchase using a credit card or mobile payment device in his/her home town, in another part of the world, or via the internet. Each transaction has a two stage process: authorization and clearing & settlement. Authorization is the process of approving or declining the transaction at the commencement of the transaction and clearing & settlement is the process of making the payment and accounting for the payment.

The authorization process begins when a point-of-sale terminal (physical for in-store purchases, virtual for internet purchases) obtains a purchaser's account information from a credit card or mobile payment device information and further obtains a transaction amount. The terminal transmits the account information and the transaction amount to an acquirer bank, which combines the account information and the transaction amount into an authorization request. The acquirer bank transmits the authorization request to a proprietary transaction processing network (e.g., VisaNet®), which routes the authorization request to an issuer bank (i.e., the bank that issued the credit card). Alternatively, the proprietary transaction processing network may perform a stand-in review and authorization.

When the authorization request is sent to the issuer bank, the bank, or a designated third party, reviews the request and approves it or denies it. The issuer bank transmits a response to the proprietary transaction processing network indicating its decision. The proprietary transaction processing network forwards the response to the acquirer bank, which in turn, forwards the response to the point-of-sale terminal.

The clearing & settlement process begins with clearing, which, in turn, begins when the point-of-sale terminal, or other merchant processing device, transmits sales draft information (e.g., account numbers and amounts) to the acquirer bank. The acquirer bank formats the sales draft information into a clearing message that it transmits to the proprietary transaction processing network. The network transmits the clearing message to the issuer bank, which calculates settlement obligations of the issuer bank, processing fees, and the amount due the acquirer bank. Settlement begins when the issuer bank transmits funds to a designated bank of the proprietary transaction processing network, which, after processing, transfers the funds to the acquirer bank.

In an alternate credit card transaction processing system, the proprietary transaction network is owned by a single issuer bank. Thus, in contrast with the previously described system, the alternative system includes only one issue bank, not a large number of issuer banks, and, as such, the issuer bank's functions and the proprietary transaction network functions previously discussed are merged. In this alternate system, the processing of the single issuer is less than the multiple issuer system but creates a processing bottleneck due to the single issuer.

The use of mobile payment devices is gaining momentum in the marketplace and consumers desire more features and ease of use. In addition, many traditional credit card users would like similar additional features that allow them to customize their use of credit cards.

Therefore, a need exists for a credit card imaging and applications thereof.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWING(S)

FIG. 1 is a schematic block diagram of an embodiment of a financial transaction network in accordance with the present invention;

FIG. 2 is a schematic block diagram of an embodiment of a mobile payment device in accordance with the present invention;

FIG. 3 is a diagram of an example of a credit image displayed on a mobile payment device in accordance with the present invention;

FIG. 4 is a logic diagram of an embodiment of a method for credit image data processing in accordance with the present invention;

FIG. 5 is a diagram of another example of a credit image in accordance with the present invention;

FIG. 6 is a logic diagram of another embodiment of a method for credit image data processing in accordance with the present invention;

FIG. 7 is a schematic block diagram of an embodiment of a contactless payment module in accordance with the present invention;

FIG. 8 is a schematic block diagram of an embodiment of a financial transaction apparatus in accordance with the present invention;

FIG. 9 is a logic diagram of another embodiment of a method for credit image data processing in accordance with the present invention;

FIG. 10 is a logic diagram of another embodiment of a method for credit image data processing in accordance with the present invention; and

FIG. 11 is a logic diagram of another embodiment of a method for credit image data processing in accordance with the present invention.

DETAILED DESCRIPTION OF THE INVENTION

FIG. 1 is a schematic block diagram of an embodiment of a financial transaction system 10 that includes a payment entity device 12, a database 14, a proprietary network 16, a plurality of proprietary interfaces 18-25, a proprietary gateway 26, a plurality of acquirer devices 28-30, a plurality of issuer devices 32-34, a public network 36 (e.g., the internet), a plurality of user devices 38-42, an plurality of merchant devices 44-52, and a plurality of mobile payment devices 54-56. The system 10 supports point of sale financial transactions, automatic payment financial transactions, mobile payment device financial transactions, user device public network based financial transactions, and/or any other type of credit account (e.g., credit card, pre-paid card, corporate card, debit card, purchasing card, mobile payment account, etc.) based financial transactions. The system 10 may also support credit account communications (e.g., account balance inquires, usage offers, bonus programs, general credit account information, etc.) via the public network 36. The system 10 may further support proprietary client services (e.g., commercial accounts payable and/or accounts receivable processing, financial reporting, etc.) for a client via its associated user device 38 and the proprietary gateway 26. Note that each of connection lines n₁-n₆ includes a plurality of individual connection lines for each device connected thereto, but are shown as a bundle for ease of illustration.

As shown, each of the issuer devices 32-34 and acquirer devices 28-30 is connected to the public network 36 and to the proprietary network 16 via a proprietary interface 18-25 to support one or more of the various financial transactions and credit account communications. For instance, a financial transaction may begin with a merchant device 44-52 (e.g., a computer, server, point of sale device, web browser application, and/or any device that facilitates a credit account based transaction) obtaining a credit account information for a point of sale transaction, an internet transaction, a mobile payment transaction, etc. In addition, the merchant device 44-52 determines a corresponding transaction amount and transmits, via a connection line, the credit account information and the transaction amount to an affiliated acquirer device 28-30.

The acquirer device 28-30 (e.g., a computer, server, etc. associated with a financial institution supporting credit account transactions of a merchant) generates an authorization request from the credit account information and the transaction amount. The acquirer device 28-30 transmits the authorization request to the payment entity device 12 via the corresponding proprietary interface 18-20 and the proprietary network 16. The payment entity device 12 accesses the associated database 14 to identify the user associated with the credit account information, an issuer, etc. Having identified the issuer, the payment entity device 12 transmits the authorization request to the appropriate issuer device 32-34 via the proprietary network 16 and the corresponding proprietary interface 22-24.

In an embodiment, the payment entity device 12, the database 14, and the proprietary network 16 may be operated and maintained by a single entity to facilitate seamless authorization and clearing & settlement. For example, Visa, Inc. may provide its VisaNet® as the proprietary network 16 and have one or more computing devices (e.g., computers, servers, super computers, main frames, etc.) coupled to the proprietary network 16 to function as the payment entity device 12, and may have one or more databases 14 coupled thereto. Further, the proprietary interfaces 18-25, which may be proprietary nodes, modems, bridges, etc., serve as secure connection points to the proprietary network 16 to ensure that only authorized devices (e.g., merchant device 44, issuer device 32-34, acquirer device 28-30) have access to the proprietary network 16.

The issuer device 32-34 (e.g., a computer, server, etc. and corresponding financial transaction software associated with a financial institution that issues credit accounts to users) processes the authorization request to determine whether to approve or deny the request. The issuer device 32-34 transmits, via the associated proprietary interface 22-24 and the proprietary network 16, an approval or denial response to the payment entity device 12. The payment entity device 12 forwards the response to the acquirer device 28-30 via the proprietary network 16 and the corresponding proprietary interface 18-20. The acquirer device 28-30 forwards the response to the merchant device 44-52 via the corresponding connection line. Note that the system 10 also supports the clearing & settlement process.

The issuer devices 32-34, the acquirer devices 28-30, and/or the payment entity device 12 support credit account communications from users via the user devices 38-42 and the public network 36, from merchants via the merchant devices 44-52 and the public network 36, etc. For example, a user device 38-42 may access a web site running on the payment entity device 12 (e.g., Visa, Inc.'s web site) to obtain information regarding various credit card offers supported by Visa, Inc. As another example, a user device 38-42 may access an issuer device 32-34 via the public network 36 to obtain current information regarding the user's account with the issuer, on-line bill payment, open a new account, etc.

In addition to accessing the payment entity device 12 via the public network 36, a user device 38 may have access to a proprietary gateway 26 to access the payment entity device 12 via the proprietary network 16 for a proprietary service (e.g., accounts payable, accounts receivable, financial reporting, elite class offers, etc.). Note that the proprietary gateway 26 may be a proprietary node, modem, bridge, etc., that serves as a public connection point to the proprietary network 16. The proprietary gateway 26 functions to ensure that only authorized entities (e.g., user device 38) have access to the proprietary network 16.

As mentioned, the system 10 may support mobile payment transactions initiated by a mobile payment device 54-56. During the processing of a credit payment transaction initiated by the mobile payment device 54-56, the mobile payment device 54-56 may obtain a credit image data and display it. The credit image data may be retrieved from memory, from a financial institution server (e.g., the payment entity device 12, an issuer device 32-34, or an acquirer device 28-30), from a contactless payment module, from a corresponding user device 38-42. etc. The processing, determining, generating, retrieving, and/or displaying of credit image data will be described in greater detail with reference to FIGS. 2-11.

FIG. 2 is a schematic block diagram of an embodiment of a mobile payment device 54-56 that includes a contact less payment module 60, a processing module 62, a display module 64, and a bus 72. The display module 64 may include a display 64 (e.g., an LCD (liquid crystal display) display, a DLP (digital light projection) display, etc.) The processing module 62 may be a single processing device or a plurality of processing devices. Such a processing device may be a microprocessor, micro-controller, digital signal processor, microcomputer, central processing unit, field programmable gate array, programmable logic device, state machine, logic circuitry, analog circuitry, digital circuitry, and/or any device that manipulates signals (analog and/or digital) based on hard coding of the circuitry and/or operational instructions. The processing module 72 may have an associated memory 70 and/or memory element, which may be a single memory device, a plurality of memory devices, and/or embedded circuitry of the processing module. Such a memory device may be a read-only memory, random access memory, volatile memory, non-volatile memory, static memory, dynamic memory, flash memory, cache memory, and/or any device that stores digital information. Note that when the processing module 62 implements one or more of its functions via a state machine, analog circuitry, digital circuitry, and/or logic circuitry, the memory 70 and/or memory element storing the corresponding operational instructions may be embedded within, or external to, the circuitry comprising the state machine, analog circuitry, digital circuitry, and/or logic circuitry. Further note that, the memory element stores, and the processing module 62 executes, hard coded and/or operational instructions corresponding to at least some of the steps and/or functions illustrated in FIGS. 2-11. Even further note that the mobile payment device 54-56 may include a wireless transceiver 74 that provides cellular (e.g., voice) and data (e.g., email, Internet access, etc.) telephone functionality for the mobile payment device 54-56.

In operation, the contactless payment module 60 executes a credit payment transaction. In general, when the contactless payment module 60 is proximal to a point of sale terminal (e.g., for point of sale transactions), the contactless payment module 60 exchanges data (e.g., account information, purchase price, etc.) with the point of sale terminal via radio frequency (RF) signals and/or electromagnetic coupling signals. For example, the contactless payment module may be a subscriber identity module (SIM) having a radio frequency identification (RFID) interface; a smart card with the RFID interface; a SIM having a near field communication (NFC) interface; and/or a smart card with the NFC interface. In addition to point of sale transactions, the contactless payment module 60 may provide a remote-based transactions (e.g., internet or Short-Message-Service (SMS) based e-commerce transactions) payment method and/or money transfers between mobile payment devices.

The processing module 60 is coupled to detect the executing of the credit payment transaction. For example, the processing module 60 detects the data exchange between the contactless payment module 60 and the point of sale terminal and/or receives a signal from the contactless payment module 60 indicating initiation of the credit payment transaction. After detecting the executing, the processing module 62 retrieves credit image data. The processing module 62 may retrieve the credit image data from memory 70 and/or from the contactless payment module 60. Alternatively, or in addition to, the processing module 62 may retrieve the credit image data from a financial institution server (e.g., the payment entity device 12, an issuer device 32-34, or an acquirer device 28-30) via the wireless transceiver 74.

As an example of retrieving the credit image data at least partially from a financial institution server, the processing module 62 sends a retrieval message to the wireless transceiver 74 upon detecting the execution of the credit payment transaction. The wireless transceiver 74 converts the retrieval message into an RF signal that is transmitted to a cellular tower (not shown), which converts the RF signal into a data message that is forwarded to the financial institution server via the public network 36. The financial institution server processes the retrieval message to identify the user, the user's credit image data and any other pertinent data. The financial institution sends the user's credit image data to the wireless transceiver 74 via the reverse path from which it received the request message. The wireless transceiver 74 recovers the credit image data from the received RF signal to produce recovered credit image data and provides the recovered credit image data to the processing module 62.

The processing module 62 coordinates the credit image data being provided to the display module 64. The graphics engine 68 (which may be a video graphics accelerator, a video decoder, an LCD driver, a DLP driver, etc.) processes the credit image data to produce a displayed credit image that is displayed via the display 66.

FIG. 3 is a diagram of an example of a credit image displayed on the display 66 of a mobile payment device 54-56. In this example, the credit image data a master image layer 80 (e.g., issuer's logo, credit card logo, cardholder's name, account number, expiration date, issuance date, etc.) and a design image layer 82 (e.g., a race car character). The design layer 82 may be a custom design image layer (e.g., a digital image provided by the user of the mobile payment device 54-56) and/or one of a plurality of approved design image layers offered by the financial institution that operates the financial institution server.

FIG. 4 is a logic diagram of an embodiment of a method for credit image data processing that may be performed by the processing module 62. The method begins at step 90 where the processing module 62 detects the executing of the credit payment transaction by the contactless payment module 60. In addition to detecting the executing of the payment transaction, the processing module 62 may detect a type of the credit payment transaction (e.g., credit card, debit card, commercial purchase card, pre-pay card, corporate card, etc.).

The method then proceeds to step 92 where the processing module 62 retrieves the credit image data based on the detecting of the executing of the credit payment transaction. The processing module 62 may retrieve the credit image data in a variety of ways. For example, the processing module 62 may retrieve the credit image data from the memory 70, which stores the credit image data and may further store a plurality of credit image data. If the memory 70 is storing a plurality of credit image data, then the processing module 62 may retrieve one of a plurality of credit image data based on the type to provide the credit card image or in accordance with a retrieval scheme (e.g., round robin, random, user's ordering, etc.). Alternatively, or in addition to, the processing module 62 may retrieve the credit image data from a financial server via the wireless transceiver 74. As yet another alternative, the processing module 62 may retrieve the credit image data from the contactless payment module 60.

The method then proceeds to step 94 where the processing module 62 sends the credit image data to the display module 64. The display module 64 processes the credit image data to render on image on the display 66.

FIG. 5 is a diagram of another example of credit image data that includes the master image layer 80, the design image layer 82, and may further include a transactional image layer 100. The transactional image layer 100 includes data relating to the current purchase (e.g., purchase amount, available balance, etc.) and other relevant data regarding the account (e.g., next payment due date, amount due, recent purchases, etc.).

The processing module 62 may receive the transactional image layer 100 from the financial institution via the wireless transceiver 74. For instance, in response to the request message sent via the wireless transceiver, the wireless transceiver receives a radio frequency (RF) signal from a financial institution server, wherein the RF signal includes the transactional data. The wireless transceiver 74 recovers the transactional data from the RF signal to produce recovered transactional data and provides the recovered transactional data to the processing module 62. The processing module 62 generates the transactional image layer 100 of the credit image data based on the recovered transactional data.

In an embodiment, the processing module 62 may process the master image layer 80 and the transactional image layer 100 such that display 66 alternates presenting the master image and the transactional image. Alternatively, the processing module 62 may process a request from the user to display one or the other of the master image and the transactional image, to jump between the two, or to not display one or more of the image layers.

FIG. 6 is a logic diagram of another embodiment of a method for credit image data processing that may be performed by the processing module 62. The method begins at step 110 where the processing module 62 detects the executing of the credit payment transaction as previously discussed. The method continues at step 112 where the processing module 62 retrieves the credit image master layer from memory in accordance with the detecting. For instance, as soon as the processing module detects the executing, it begins the retrieval process. Note that the processing module 62 may retrieve the master image layer from memory 70, from a financial institution server via the wireless transceiver 74, and/or from the contactless payment module 60.

The method then proceeds to step 114 where the processing module 62 retrieves one of the plurality of digital images from memory 70 in accordance with the detecting. The retrieval may further be done in accordance with a retrieval scheme. Note that the mobile payment device 54-56 may be a cellular telephone with a built-in digital camera such that the digital images stored in memory 70 are a collection of pictures taken by an operator of the device 54-56. As part of the retrieval process, the processing module 62 may perform an appropriateness check of the image before providing it to the display module 64.

Such a check begins at step 118 where the processing module 62 determines content of the digital image. The method continues at step 120 where the processing module 62 analyzes the content of the image to determine whether it contains inappropriate content. For example, the processing module 62 may perform an image recognition algorithm to identify potentially inappropriate objects within the image. If, at step 122, the image does not include inappropriate content, the method continues at step 124 where the processing module retrieves the digital image from memory and provides it to the display module 64. If, however, the image potentially includes inappropriate content, the method proceeds to step 126 where the processing module selections another digital image for appropriateness checking.

The method then proceeds to step 116 where the processing module 62 generates credit image data based on the credit image master layer and the one of the plurality of digital images. The processing module 62 may further process a transactional image layer into the credit image data, wherein the transactional image layer is based on recovered transactional data.

FIG. 7 is a schematic block diagram of an embodiment of a contactless payment module 60 that includes a key module 130, memory 132, a contactless interface 134, and a memory interface 136. The key module 130 contains a unique subscriber identification code and credit transactional information in accordance with a mobile payment protocol. In an embodiment, the unique subscriber identification code may be an International Mobile Subscriber Identity (IMSI). The contactless interface 134 transmits at least one of the unique subscriber identification code and the credit transactional information during execution of a credit transaction. In an embodiment, the contactless interface a radio frequency identification (RFID) interface and/or a near field communication (NFC) interface.

The memory 132, which may be memory as previously defined, stores a credit image data that may be retrieved via the memory interface 136 by the processing module 62 or other device, module, etc. The credit image data includes a master image layer and a design image layer, which may be a custom design image layer and/or one of a plurality of approved design image layers.

FIG. 8 is a schematic block diagram of an embodiment of a financial transaction apparatus 140, which may be included within, or associated with, the payment entity device 12, an issuer device 32-34, and/or an acquirer device 28-30. The apparatus 140 includes a processing module 142, memory 144, and an interface 146, which may be a wireless and/or a wired interface that enables the apparatus 140 to access the public network 36. The processing module 142 may be a single processing device or a plurality of processing devices. Such a processing device may be a microprocessor, micro-controller, digital signal processor, microcomputer, central processing unit, field programmable gate array, programmable logic device, state machine, logic circuitry, analog circuitry, digital circuitry, and/or any device that manipulates signals (analog and/or digital) based on hard coding of the circuitry and/or operational instructions. The processing module 142 may have an associated memory 144 and/or memory element, which may be a single memory device, a plurality of memory devices, and/or embedded circuitry of the processing module. Such a memory device may be a read-only memory, random access memory, volatile memory, non-volatile memory, static memory, dynamic memory, flash memory, cache memory, and/or any device that stores digital information. Note that when the processing module 142 implements one or more of its functions via a state machine, analog circuitry, digital circuitry, and/or logic circuitry, the memory 144 and/or memory element storing the corresponding operational instructions may be embedded within, or external to, the circuitry comprising the state machine, analog circuitry, digital circuitry, and/or logic circuitry. Further note that, the memory element stores, and the processing module 142 executes, hard coded and/or operational instructions corresponding to at least some of the steps and/or functions illustrated in FIGS. 9-11.

FIG. 9 is a logic diagram of another embodiment of a method for credit image data processing that may be processed by the processing module 142. The method begins at step 150 where the processing module 142 receives, via the interface 146, a digital image from a user via a user device 38-42 and/or via a mobile payment device 54-56. The method then proceeds to step 152 where the processing module 142 determines content of the digital image. The method continues at step 154 where the processing module 142 analyzes the content of the digital image to determine whether it contains inappropriate content. This may be done use image recognition software to identify potentially inappropriate objects, gestures, etc. within the digital image.

If the digital image does not include inappropriate content, the method branches from step 156 to step 158 where the processing module 142 generates a design image layer based on the digital image. The method continues at step 160 where the processing module retrieves from memory 144 a master image layer. The method continues at step 162 where the processing module 142 processes the design image layer and the master image layer to produce credit image data. The method continues at step 164 where the processing module 142 transmits, via the interface 146, the credit image data.

If the digital image does include inappropriate content, the method branches from step 156 to step 166 where the processing module 142 rejects the present digital image and begins processing another if one is available.

FIG. 10 is a logic diagram of another embodiment of a method for credit image data processing that begins at step 170 where the processing module 142 receives, via the interface 146, an indication of execute of a credit payment transaction by a mobile payment device. The method continues at step 172 where the processing module 142 determines identity of a mobile payment device based on the indication. The method continues at step 174 where the processing module 142 generates a transactional data image layer based on at least one of transactional data of the mobile payment device and the credit payment transaction. The method continues at step 176 where the processing module 142 generates the credit image data based on the design image layer, the master image layer, and the transactional data image layer. The method continues at step 178 where the processing module 142 transmits, via the interface 146, the credit image data to the mobile payment device.

FIG. 11 is a logic diagram of another embodiment of a method for credit image data processing that begins at step 180 where the processing module 142 receives, via the interface 146, a request for credit image data from a mobile payment device. The method continues at step 182 where the processing module 142 retrieves the credit image data based on identity of mobile payment device. The method continues at step 184 where the processing module 142 provides, via the interface 142, the credit image data to the mobile payment device. The credit image data may include a master image layer and a design image layer, which may be a custom design image layer and/or one of a plurality of approved design image layers.

In addition to steps 180-184, the processing module 142 may further function to: receive, via the interface 146, an indication of execute of a credit payment transaction from the mobile payment device; generate a transactional data image layer based on at least one of transactional data of the mobile payment device and the credit payment transaction; and generate the credit image data based on the design image layer, the master image layer, and the transactional data image layer.

As may be used herein, the terms “substantially” and “approximately” provides an industry-accepted tolerance for its corresponding term and/or relativity between items. Such an industry-accepted tolerance ranges from less than one percent to fifty percent and corresponds to, but is not limited to, component values, integrated circuit process variations, temperature variations, rise and fall times, and/or thermal noise. Such relativity between items ranges from a difference of a few percent to magnitude differences. As may also be used herein, the term(s) “coupled to” and/or “coupling” and/or includes direct coupling between items and/or indirect coupling between items via an intervening item (e.g., an item includes, but is not limited to, a component, an element, a circuit, and/or a module) where, for indirect coupling, the intervening item does not modify the information of a signal but may adjust its current level, voltage level, and/or power level. As may further be used herein, inferred coupling (i.e., where one element is coupled to another element by inference) includes direct and indirect coupling between two items in the same manner as “coupled to”. As may even further be used herein, the term “operable to” indicates that an item includes one or more of power connections, input(s), output(s), etc., to perform one or more its corresponding functions and may further include inferred coupling to one or more other items. As may still further be used herein, the term “associated with”, includes direct and/or indirect coupling of separate items and/or one item being embedded within another item. As may be used herein, the term “compares favorably”, indicates that a comparison between two or more items, signals, etc., provides a desired relationship. For example, when the desired relationship is that signal 1 has a greater magnitude than signal 2, a favorable comparison may be achieved when the magnitude of signal 1 is greater than that of signal 2 or when the magnitude of signal 2 is less than that of signal 1.

The present invention has also been described above with the aid of method steps illustrating the performance of specified functions and relationships thereof. The boundaries and sequence of these functional building blocks and method steps have been arbitrarily defined herein for convenience of description. Alternate boundaries and sequences can be defined so long as the specified functions and relationships are appropriately performed. Any such alternate boundaries or sequences are thus within the scope and spirit of the claimed invention.

The present invention has been described above with the aid of functional building blocks illustrating the performance of certain significant functions. The boundaries of these functional building blocks have been arbitrarily defined for convenience of description. Alternate boundaries could be defined as long as the certain significant functions are appropriately performed. Similarly, flow diagram blocks may also have been arbitrarily defined herein to illustrate certain significant functionality. To the extent used, the flow diagram block boundaries and sequence could have been defined otherwise and still perform the certain significant functionality. Such alternate definitions of both functional building blocks and flow diagram blocks and sequences are thus within the scope and spirit of the claimed invention. One of average skill in the art will also recognize that the functional building blocks, and other illustrative blocks, modules and components herein, can be implemented as illustrated or by discrete components, application specific integrated circuits, processors executing appropriate software and the like or any combination thereof. 

1.-29. (canceled)
 30. A method comprising: detecting, by a processor in a mobile device, an initiation of a transaction using the mobile device; sending, by the processor, a retrieval message to a remote server computer via a communications network, the retrieval message including an identifier associated with the mobile device, wherein the remote server computer receives the retrieval message from the mobile device, retrieves a transactional image layer from a memory based on the identifier associated with the mobile device, and provides the transactional image layer to the mobile device; and displaying, by the processor, image data including the transactional image layer and a master image layer via a display of the mobile device.
 31. The method of claim 30, wherein the transactional image layer includes at least one of transactional data associated with the mobile device and transactional data for the transaction.
 32. The method of claim 30, wherein the mobile device is a mobile phone.
 33. The method of claim 30, wherein the transactional image layer comprises an available balance associated with the identifier for the mobile device.
 34. The method of claim 30, further comprising: converting, by a wireless transceiver of the mobile device, the retrieval message to an RF signal prior to sending the retrieval message to the remote server computer.
 35. The method of claim 30, wherein the communications network is a wireless communications network.
 36. The method of claim 30, wherein the transactional image layer comprises data relating to a current purchase.
 37. The method of claim 30, wherein the remote server computer further: retrieves the master image layer from a memory based on the identifier associated with the mobile device, processes the master image layer and the transactional image layer to generate the image data, and transmits the image data to the mobile device.
 38. The method of claim 30, wherein the master image layer is retrieved from a memory in the mobile device.
 39. The method of claim 30, wherein the master image layer is retrieved from a memory in the mobile device, and the processor in the mobile device generates the image data.
 40. A mobile device comprising: a processor; and a display coupled to the processor; a non-transitory computer-readable storage medium coupled to the processor, comprising code executable by the processor for implementing a method comprising: detecting, by the processor in the mobile device, an initiation of a transaction using the mobile device; sending, by the processor, a retrieval message to a remote server computer via a communications network, the retrieval message including an identifier associated with the mobile device, wherein the remote server computer receives the retrieval message from the mobile device, retrieves a transactional image layer from a memory based on the identifier associated with the mobile device, and provides the transactional image layer to the mobile device; and displaying, by the processor, image data including the transactional image layer and a master image layer via the display of the mobile device.
 41. The mobile device of claim 40, wherein the transactional image layer includes at least one of transactional data associated with the mobile device and transactional data for the transaction.
 42. The mobile device of claim 40, wherein the mobile device is a mobile phone.
 43. The mobile device of claim 40, wherein the transactional image layer comprises an available balance associated with the identifier for the mobile device.
 44. The mobile device of claim 40, wherein the method further comprises: converting, by a wireless transceiver of the mobile device, the retrieval message to an RF signal prior to sending the retrieval message to the remote server computer.
 45. The mobile device of claim 40, wherein the communications network is a wireless communications network.
 46. The mobile device of claim 40, wherein the transactional image layer comprises data relating to a current purchase.
 47. The mobile device of claim 40, wherein the remote server computer further: retrieves the master image layer and the transactional image layer from a memory based on the identifier associated with the mobile device, processes the master image layer and the transactional image layer to generate the image data, and transmits the image data to the mobile device.
 48. The mobile device of claim 40, wherein the master image layer is retrieved from a memory in the mobile device.
 49. The mobile device of claim 40, wherein the master image layer is retrieved from a memory in the mobile device, and the processor in the mobile device generates the image data. 